boot [-file filename] [-flags longword[,longword]] [-protocols enet_protocol] [-halt] [boot_device]
Description |
Examples |
Where:
| -file filename | Specifies the name of a file to load into the system. For booting from Ethernet, this name is limited to 15 characters. Use the set boot_file command to set an environment variable that specifies a default boot file. |
| -flags data | Specifies additional information
for the operating system. Use the set boot_osflags command to set an environment
variable that specifies a default boot flag values. OpenVMS boot flags. Tru64 UNIX boot flags. |
| -protocols enet_protocol | Specifies an Ethernet protocol(s) that will be used for a network boot. Values may be mop or bootp. |
| -halt | Forces the bootstrap operation to halt and invoke the console program after the image is loaded and the page tables and other data structures are set up. |
| boot_device | Specifies a device path or list of devices that the firmware will attempt to boot. Use the set bootdef_dev command to set an environment variable that specifies a default boot device. |
| >>>boot | Boots the system from the default boot device. |
| >>>boot ewa0 | Boots the system from Ethernet port ewa0. |
| >>>boot -file dec2.sys ewa0 | Boots the file named dec2.sys from Ethernet port ewa0. |
| >>>boot -protocol bootp ewa0 | Boots using TCP/IP BOOTP protocol from Ethernet post ewa0. (Make sure the environment variables ewa0_protocols and ewa0_inet_init are both set to BOOTP before booting.) |
| >>>boot -flags a | Boots the system from the default boot device using flag settings 0,1. |
| >>>boot -halt dka0 | Loads the image from disk dka0, but remains in console mode. |
| >>> boot Trying MOP boot. ... ... ... | Successful boot from a system that is set to secure mode. In this example the boot command is equivalent to:(boot eza0.0.6.0 -file myfile.sys -flags 0) |
The OpenVMS boot flags consist of two portions separated by a comma: root , bootflag. The value may be stored in the boot_osflags variable or typed in when booting. The default value is 0,0. The left half specifies the directory to boot from (0 = [SYS0], 1 = [SYS1] and so forth). The right half can be used to enable specific functions during booting as shown below:
| Value | Bit | Description |
|---|---|---|
| 1 | 0 | Conversational boot (SYSBOOT>). |
| 2 | 1 | Maps XDELTA to a running system. |
| 4 | 2 | Stops at the initial system breakpoint. |
| 8 | 3 | Performs a diagnostic bootstrap. |
| 10 | 4 | Stops at the bootstrap breakpoints. |
| 20 | 5 | Omits header from secondary boot image. |
| 80 | 7 | Prompts for the name of the secondary bootfile. |
| 100 | 8 | Halts the system before secondary bootstrap. |
| 2000 | 13 | Marks corrected read data error pages as bad. |
| 10000 | 16 | Displays extensive debug messages during booting. |
| 20000 | 17 | Displays selected user messages during booting. |
Tru64 UNIX boot flags can be stored in the boot_osflags variable or typed in along with the boot command. The possible boot flags for Tru64 UNIX are:
| Flag | Description |
|---|---|
| Load OS from the specified boot device. Boot to multiuser mode. | |
| Prompt for the name of a file to load and other options (Boot interactively). Boot to single user mode. | |
| Stop in single user mode. Boot /vmunix to single user mode and stop at the # (root) prompt. | |
| Full dump, implies "s" as well. |